-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix expo config plugin #161
Conversation
Yeah this is broken and should be merged ASAP @uddish |
the only way i can think to make this work (quickly...) is to just completely remove importing the package.json from inside of the expo plugins file.
we just can't have a relative import like that if so, my great suggestion would be to just remove import package.json there, at the bottom of the
then in side of the
|
Thanks, this sounds like a good solution. I tried to push commits for this now. |
👏 seems alright to me there's probably a less dumb way of doing it but the |
Could we merge it ? im having issues with sdk 50 |
@ottob seems is failing on lint step in CI |
get rid of relative import path of package.json idea from @tomfinney
fixed the lint issue now |
@ottob thank you so much |
My boss is waiting for a feature in our app that wont work until this is merged, you guys are life savers if you can get it merged today or tomorrow! |
Hey @ottob |
No, but I have basically the same change locally, and it works. And it can not get more broken than it is :) And I can test it directly when you release a new version. |
Ive tested it now locally, and it works for me. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! Thanks for your work on this folks. Will get this merged in now.
Thank you so much @MikeMcNamara |
Version has been bumped now in npm! |
I just tested the plugin with 6.8.0 and it works! I had just to replace Thank you all for your work! ❤️ we can finally to switch to an official up-to-date plugin! |
@MikeMcNamara two steps forward, one step back 😀 |
Thanks for this! |
get rid of relative import path of package.json idea from @tomfinney Co-authored-by: Mike McNamara <[email protected]>
But there is still an error:
since
intercom-react-native/src/expo-plugins/index.ts
Line 19 in f75b38c
should be
because after the build the file ends up in /lib/commonjs/expo-plugins/index.js so it needs to step back three folders.
not sure how to fix that...